Fix: DoS Attack via Range Requests - #327
Open
WesternConcrete wants to merge 1 commit into
Open
WesternConcrete wants to merge 1 commit into
WesternConcrete wants to merge 1 commit into
Conversation
Co-Authored-By: Wes Convery <2wconvery@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Finding: DoS Attack via Range Requests (CVE-2018-15756, https://spring.io/security/cve-2018-15756)
Repo: COG-GTM/ftgo-monolith
Spring Boot 2.0.3.RELEASE manages Spring Framework 5.0.7, whose
ResourceHttpRequestHandleris vulnerable to DoS via many/overlappingRangeheaders;ftgo-applicationserves static resources (static/index.html,js/app.js,css/style.css) so the handler is active.Fix approach: bump
springBootVersioningradle.propertiesfrom2.0.3.RELEASEto2.0.9.RELEASE(the final 2.0.x patch), which manages Spring Framework 5.0.13 (>= 5.0.10 where the issue was fixed) while staying on the same Spring Boot minor line and Gradle 4.10 wrapper.Note: local Gradle build could not be verified in this session because Maven Central returned HTTP 429 (rate limited) for all artifact downloads; relying on CI.
Link to Devin session: https://app.devin.ai/sessions/2aa54ffd887c442a8c8a716040545202
Open in Devin Desktop: https://app.devin.ai/desktop/session/2aa54ffd887c442a8c8a716040545202?variant=devin
Requested by: @WesternConcrete